|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Standards Track - Draft Standard (November 1990)
|
|
3.
|
Justification for the specific reference:
|
|
|
required by CA/Browser Forum
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=1191
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
at least two independent, interoperable implementations and sufficient successful operational experience exist; if IPR issues are known, then independent implementations must be based on at least two separate exercises of the licensing process; considered mature and final form of specification
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Standards Track - Draft Standard (November 1990). Legacy document stream. Obsoletes RFC 1063.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 1191 obsoletes RFC 1063
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] R. Braden, ed. Requirements for Internet Hosts -- Communication/
Layers. RFC 1122, SRI Network Information Center, October, 1989./
/
[2] Geof Cooper. IP Datagram Sizes. Electronic distribution of the/
TCP-IP Discussion Group, Message-ID/
8705240517.AA01407@apolling.imagen.uucp./
/
[3] ISO. ISO Transport Protocol Specification: ISO DP 8073. RFC 905,/
SRI Network Information Center, April, 1984./
/
[4] Van Jacobson. Congestion Avoidance and Control. In Proc. SIGCOMM/
'88 Symposium on Communications Architectures and Protocols, pages/
314-329. Stanford, CA, August, 1988./
/
[5] C. Kent and J. Mogul. Fragmentation Considered Harmful. In Proc./
SIGCOMM '87 Workshop on Frontiers in Computer Communications/
Technology. August, 1987./
/
[6] Drew Daniel Perkins. Private Communication./
/
[7] J. Postel. Internet Control Message Protocol. RFC 792, SRI/
Network Information Center, September, 1981./
/
[8] J. Postel. Internet Protocol. RFC 791, SRI Network Information/
Center, September, 1981./
/
[9] J. Postel. The TCP Maximum Segment Size and Related Topics. RFC/
879, SRI Network Information Center, November, 1983./
/
[10] Michael Reilly. Private Communication./
/
[11] Sun Microsystems, Inc. RPC: Remote Procedure Call Protocol. RFC/
1057, SRI Network Information Center, June, 1988.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
